Better update process
Reported by Aurelien Botman | October 24th, 2010 @ 09:55 PM
Not a bug per se, but when updates are applied to the tilige server, we are just hoping that no user is currently active. So if updates are applied (which may cause undesired behavior while the various bits are still cached) some user confusion may occur.
We could solve this by (1) having a clock of when the tilige backend was last busy at, and on the admin side just assume that if no user has asked for the backend to process something in the last 15 minutes we are clear to apply the update, and (2) during the actual update, shutdown the public facing portion, or at least pop up a maintenance page.
Note we still have to find a good way to invalidate the old cache. Calling the bits with a version number each time may help.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
This is the bug reporting and support system for tilige.com.